Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DietPi-Build | Add support for Sparky SBC #6391

Merged
merged 1 commit into from
May 27, 2023
Merged

DietPi-Build | Add support for Sparky SBC #6391

merged 1 commit into from
May 27, 2023

Conversation

MichaIng
Copy link
Owner

No description provided.

@MichaIng
Copy link
Owner Author

@davindisko @seniorgod @bamyasi @Balmoral86
If you still use or have the Sparky SBC around and fine time, could you test the new image(s) I created? The kernel did not change, so Docker support is most likely still broken as long as systemd.unified_cgroup_hierarchy=0 kernel command-line argument does not help (which is not added OOTB). But I added kernel, initramfs and the Sparky specific configs to a DEB package and the image is now cleanly built from scratch via debootstrap in our CI: https://github.com/MichaIng/DietPi/actions/runs/5073112164/jobs/9111901713
This makes it a lot cleaner compared to the old image which got just updated over years. However, since I do not know have the bootloader binary, I just flashed all bits before first partition, excluding MBR. It should work, but good to assure that on a real Sparky SBC before moving it to stable downloads. The image built with above workflow can be found here: https://dietpi.com/downloads/images/testing/

- DietPi-Build | Add support for Sparky SBC
@MichaIng
Copy link
Owner Author

Merging it, however will leave the new Sparky SBC images in testing until someone actually tested them.

@MichaIng MichaIng merged commit 14ef809 into dev May 27, 2023
@MichaIng MichaIng deleted the sparkysbc branch May 27, 2023 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant